Preserve unsafe async reads with packed frame buffers - #106

When unsafe async moves a running bot from the live buffer to a packed frame, #105 can calculate an offset using one layout and read it using the other. Retained Event, Position, Command, and UnitCommand views also keep layout-dependent offsets across the handoff. This can return incorrect data or access invalid native memory.

Keep all generated offsets in the original BWAPI layout and translate them inside the selected WrappedBuffer at the primitive/string access. Publish ClientData.buffer through a volatile reference, remove the redundant dynamic overrides, and update the generator. Static-data routing, the four copy ranges, and unsafe async's start-before-copy scheduling stay unchanged. Packed slots remain 4,805,308 bytes instead of 33,017,048 bytes.

This PR is based on #105 (a1574049) and targets its implement-memory-safe branch.

Validation:

• Both handoff regression tests fail on Reduce Async FrameBuffer memory usage #105 and pass with this fix.
• All 52 tests pass on Java 8, with automatic retries disabled.
• The new synchronization test holds the first frame copy until the bot starts, proving unsafe overlap is preserved; the game then completes across multiple buffer cycles.
• All 10 focused AsyncClientData/WrappedBuffer/UnsafeTools tests pass on Java 27.
• Generator output is byte-for-byte reproducible; existing file line endings are preserved.